CI: fix DovesLapTimer pin to v4.1.0 — #62 merged before the correction landed#65
Merged
Merged
Conversation
…0, not v2.3.1
v2.3.1 doesn't exist in the DovesLapTimer repo, so the library checkout
failed ('pathspec v2.3.1 did not match any file(s)') and the
compile-sketch jobs went down before compiling anything. Docs updated to
match.
https://claude.ai/code/session_01Voi2VL5zjikyhEqgTvzmAL
Coverage — host-testable units📂 Overall coverage
📄 File coverage
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #62, which was merged a few minutes before the tag-name correction landed on its branch — so BETA still carries the nonexistent
v2.3.1DovesLapTimer pin while master got the correctedv4.1.0via #63.This cherry-picks that exact correction (
v2.3.1→v4.1.0incompile-sketch.yml,release.yml, CHANGELOG, CLAUDE.md — the tag the library actually has).Why it matters even though BETA builds don't use the tag path day-to-day: the next BETA→master merge would overwrite master's fixed workflows with the broken literal and re-break master CI and release builds (
git checkout v2.3.1→pathspec did not match, the exact failure #63's first run hit). This also restores the two branches to identical workflow content so that merge stays clean.https://claude.ai/code/session_01Voi2VL5zjikyhEqgTvzmAL
Generated by Claude Code